Techniques and apparatuses for supplementary uplink random access configuration

ABSTRACT

Certain aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment may receive RACH configuration information on a downlink carrier of a first set of carriers, wherein the RACH configuration information pertains to the first set of carriers and to a second set of carriers; and selectively perform a RACH procedure with regard to the first set of carriers or the second set of carriers based at least in part on the RACH configuration information. Numerous other aspects are provided.

CROSS-REFERENCE TO RELATED APPLICATIONS UNDER 35 U.S.C. § 119

This application claims priority to Provisional Patent Application No.62/524,159, filed on Jun. 23, 2017, entitled “TECHNIQUES AND APPARATUSESFOR SUPPLEMENTAL UPLINK RANDOM ACCESS CONFIGURATION,” which is herebyexpressly incorporated by reference herein.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wirelesscommunication, and more particularly to techniques and apparatuses forsupplementary uplink random access configuration.

BACKGROUND

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (e.g., bandwidth,transmit power, etc.). Examples of such multiple-access technologiesinclude code division multiple access (CDMA) systems, time divisionmultiple access (TDMA) systems, frequency-division multiple access(FDMA) systems, orthogonal frequency-division multiple access (OFDMA)systems, single-carrier frequency-division multiple access (SC-FDMA)systems, time division synchronous code division multiple access(TD-SCDMA) systems, and Long Term Evolution (LTE). LTE/LTE-Advanced is aset of enhancements to the Universal Mobile Telecommunications System(UMTS) mobile standard promulgated by the Third Generation PartnershipProject (3GPP).

A wireless communication network may include a number of base stations(BSs) that can support communication for a number of user equipment(UEs). A UE may communicate with a BS via the downlink and uplink. Thedownlink (or forward link) refers to the communication link from the BSto the UE, and the uplink (or reverse link) refers to the communicationlink from the UE to the BS. As will be described in more detail herein,a BS may be referred to as a Node B, a gNB, an access point (AP), aradio head, a transmit receive point (TRP), a new radio (NR) BS, a 5GNode B, and/or the like.

The above multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent user equipment to communicate on a municipal, national,regional, and even global level. New radio (NR), which may also bereferred to as 5G, is a set of enhancements to the LTE mobile standardpromulgated by the Third Generation Partnership Project (3GPP). NR isdesigned to better support mobile broadband Internet access by improvingspectral efficiency, lowering costs, improving services, making use ofnew spectrum, and better integrating with other open standards usingorthogonal frequency division multiplexing (OFDM) with a cyclic prefix(CP) (CP-OFDM) on the downlink (DL), using CP-OFDM and/or SC-FDM (e.g.,also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) onthe uplink (UL), as well as supporting beamforming, multiple-inputmultiple-output (MIMO) antenna technology, and carrier aggregation.However, as the demand for mobile broadband access continues toincrease, there exists a need for further improvements in LTE and NRtechnologies. Preferably, these improvements should be applicable toother multiple access technologies and the telecommunication standardsthat employ these technologies.

SUMMARY

In some aspects, a method for wireless communication may includereceiving random access channel (RACH) configuration information on adownlink carrier of a first set of carriers, wherein the RACHconfiguration information pertains to the first set of carriers and to asecond set of carriers; and selectively performing a RACH procedure withregard to the first set of carriers or the second set of carriers basedat least in part on the RACH configuration information.

In some aspects, a user equipment for wireless communication may includea memory and one or more processors configured to receive RACHconfiguration information on a downlink carrier of a first set ofcarriers, wherein the RACH configuration information pertains to thefirst set of carriers and to a second set of carriers; and selectivelyperform a RACH procedure with regard to the first set of carriers or thesecond set of carriers based at least in part on the RACH configurationinformation.

In some aspects, a non-transitory computer-readable medium may store oneor more instructions for wireless communication. The one or moreinstructions, when executed by one or more processors of a userequipment, may cause the one or more processors to receive RACHconfiguration information on a downlink carrier of a first set ofcarriers, wherein the RACH configuration information pertains to thefirst set of carriers and to a second set of carriers; and selectivelyperform a RACH procedure with regard to the first set of carriers or thesecond set of carriers based at least in part on the RACH configurationinformation.

In some aspects, an apparatus for wireless communication may includemeans for receiving RACH configuration information on a downlink carrierof a first set of carriers, wherein the RACH configuration informationpertains to the first set of carriers and to a second set of carriers;and means for selectively performing a RACH procedure with regard to thefirst set of carriers or the second set of carriers based at least inpart on the RACH configuration information.

Aspects generally include a method, apparatus, system, computer programproduct, non-transitory computer-readable medium, user equipment,wireless communication device, and processing system as substantiallydescribed herein with reference to and as illustrated by theaccompanying specification and drawings.

The foregoing has outlined rather broadly the features and technicaladvantages of examples according to the disclosure in order that thedetailed description that follows may be better understood. Additionalfeatures and advantages will be described hereinafter. The conceptionand specific examples disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present disclosure. Such equivalent constructions do notdepart from the scope of the appended claims. Characteristics of theconcepts disclosed herein, both their organization and method ofoperation, together with associated advantages will be better understoodfrom the following description when considered in connection with theaccompanying figures. Each of the figures is provided for the purpose ofillustration and description, and not as a definition of the limits ofthe claims.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above-recited features of the presentdisclosure can be understood in detail, a more particular description,briefly summarized above, may be had by reference to aspects, some ofwhich are illustrated in the appended drawings. It is to be noted,however, that the appended drawings illustrate only certain typicalaspects of this disclosure and are therefore not to be consideredlimiting of its scope, for the description may admit to other equallyeffective aspects. The same reference numbers in different drawings mayidentify the same or similar elements.

FIG. 1 is a block diagram conceptually illustrating an example of awireless communication network, in accordance with certain aspects ofthe present disclosure.

FIG. 2 shows a block diagram conceptually illustrating an example of abase station in communication with a user equipment (UE) in a wirelesscommunication network, in accordance with certain aspects of the presentdisclosure.

FIG. 3 is a block diagram conceptually illustrating an example of aframe structure in a wireless communication network, in accordance withcertain aspects of the present disclosure.

FIG. 4 is a block diagram conceptually illustrating two example subframeformats with the normal cyclic prefix, in accordance with certainaspects of the present disclosure.

FIG. 5 illustrates an example logical architecture of a distributedradio access network (RAN), in accordance with certain aspects of thepresent disclosure.

FIG. 6 illustrates an example physical architecture of a distributedRAN, in accordance with certain aspects of the present disclosure.

FIG. 7 is a diagram illustrating an example of a downlink (DL)-centricsubframe, in accordance with certain aspects of the present disclosure.

FIG. 8 is a diagram illustrating an example of an uplink (UL)-centricsubframe, in accordance with certain aspects of the present disclosure.

FIGS. 9A-9E are diagrams illustrating examples of supplementary uplinkrandom access configuration, in accordance with various aspects of thepresent disclosure.

FIG. 10 is a diagram illustrating an example process performed, forexample, by a user equipment, in accordance with various aspects of thepresent disclosure.

DETAILED DESCRIPTION

A UE may perform a RACH procedure to synchronize with a BS in an uplinkdirection. For example, the UE may transmit a first message (e.g., arandom access preamble) on the uplink that includes a preambleidentifier and a random access radio network temporary identifier(RA-RNTI). The UE may listen for a second message from the BS (e.g., arandom access response or RAR) that identifies a grant of resourcesreserved for the UE, along with a timing advance, the preambleidentifier, transmit power control (TPC) information, and a temporarycell RNTI (T-C-RNTI or TC-RNTI) requesting for the UE to transmit aradio resource control (RRC) connection request. After receiving thesecond message, the UE may transmit the RRC connection request on theresources as a third message, and may receive, from the BS, a permanentidentifier (e.g., a C-RNTI). Thus, synchronization is performed and anRRC connection is established in the uplink direction. Synchronizationmay be performed in the downlink direction (e.g., synchronization of theUE with the network) using the PSS and SSS transmitted by the BS beforethe RACH procedure is performed.

A UE, such as a UE using a NR radio access technology (RAT), may use asupplementary uplink (SUL) configuration. In a SUL configuration, the UEmay connect to a primary uplink carrier at a first frequency band, andmay connect to a supplementary uplink carrier at a second frequency banddifferent from the first frequency band. In some aspects, the firstfrequency band may be a time division duplexing (TDD) frequency band ora frequency division duplexing (FDD) frequency band. In some aspects,the second frequency band may be a TDD frequency band, may be an FDDfrequency band, or may be an uplink-only frequency band. Additionally,or alternatively, the first frequency band and/or the second frequencyband may be associated with respective downlink carriers. The primaryuplink carrier and the downlink carrier of the first frequency band maybe termed a first set of carriers, and the supplementary uplink carrierand the downlink carrier (when present) of the second frequency band maybe termed a second set of carriers.

One advantage of using SUL is that the second set of carriers, of thesecond frequency band, may have better coupling loss than the first setof carriers due to a lower path loss and a smaller penetration loss.This may provide improved range and uplink performance on the secondfrequency band. Also, the second frequency band may be narrower than thefirst frequency band, so for a UE with a limited bandwidth requirement(e.g., based at least in part on link budget or packet size), it may bemore spectrally efficient to use the second frequency band.

However, SUL may lead to certain difficulties for RACH configuration ofthe UE 120. For example, the first set of carriers and the second set ofcarriers may have different uplink coverage due to a difference incoupling loss between the first set of carriers and the second set ofcarriers. Furthermore, the supplementary uplink carrier may have lessaccurate RACH open loop power control than the primary uplink carrier.For example, the supplementary uplink carrier may not have a paireddownlink carrier, or, if the supplementary uplink carrier has a paireddownlink carrier, the UE 120 may not measure or connect to the paireddownlink carrier. Therefore, it may be difficult to provide RACHconfiguration information for the second set of carriers and, thus, itmay be difficult to perform RACH configuration of the second set ofcarriers.

Techniques and apparatuses described herein may provide RACHconfiguration information for the second set of carriers on a downlinkcarrier of the first set of carriers, and may selectively perform a RACHprocedure with regard to the first set of carriers or the second set ofcarriers, wherein the RACH procedure is performed using the RACHconfiguration information. For example, when the UE is capable of usingthe second set of carriers as a supplementary uplink carrier, the UE maytransmit uplink RACH messages (e.g., the first and third messages) usingthe second set of carriers. In some aspects, the UE may interpret theRACH configuration information and/or a second message of the RACHprocedure differently for the supplementary uplink carrier than for theprimary uplink carrier, which improves performance of the RACH procedureon the supplementary uplink carrier and mitigates inaccuracy in the RACHprocedure caused by the difference in coupling loss between the primaryuplink carrier and the supplementary uplink carrier. Thus, RACHperformance is improved and RACH configuration of the UE using thesupplementary uplink carrier is enabled.

Various aspects of the disclosure are described more fully hereinafterwith reference to the accompanying drawings. This disclosure may,however, be embodied in many different forms and should not be construedas limited to any specific structure or function presented throughoutthis disclosure. Rather, these aspects are provided so that thisdisclosure will be thorough and complete, and will fully convey thescope of the disclosure to those skilled in the art. Based on theteachings herein one skilled in the art should appreciate that the scopeof the disclosure is intended to cover any aspect of the disclosuredisclosed herein, whether implemented independently of or combined withany other aspect of the disclosure. For example, an apparatus may beimplemented or a method may be practiced using any number of the aspectsset forth herein. In addition, the scope of the disclosure is intendedto cover such an apparatus or method which is practiced using otherstructure, functionality, or structure and functionality in addition toor other than the various aspects of the disclosure set forth herein. Itshould be understood that any aspect of the disclosure disclosed hereinmay be embodied by one or more elements of a claim.

Several aspects of telecommunication systems will now be presented withreference to various apparatuses and techniques. These apparatuses andtechniques will be described in the following detailed description andillustrated in the accompanying drawings by various blocks, modules,components, circuits, steps, processes, algorithms, etc. (collectivelyreferred to as “elements”). These elements may be implemented usinghardware, software, or combinations thereof. Whether such elements areimplemented as hardware or software depends upon the particularapplication and design constraints imposed on the overall system.

It is noted that while aspects may be described herein using terminologycommonly associated with 3G and/or 4G wireless technologies, aspects ofthe present disclosure can be applied in other generation-basedcommunication systems, such as 5G and later, including NR technologies.

FIG. 1 is a diagram illustrating a network 100 in which aspects of thepresent disclosure may be practiced. The network 100 may be an LTEnetwork or some other wireless network, such as a 5G or NR network.Wireless network 100 may include a number of BSs 110 (shown as BS 110 a,BS 110 b, BS 110 c, and BS 110 d) and other network entities. A BS is anentity that communicates with user equipment (UEs) and may also bereferred to as a base station, a NR BS, a Node B, a gNB, a 5G NB, anaccess point, a transmit receive point (TRP), and/or the like. Each BSmay provide communication coverage for a particular geographic area. In3GPP, the term “cell” can refer to a coverage area of a BS and/or a BSsubsystem serving this coverage area, depending on the context in whichthe term is used.

A BS may provide communication coverage for a macro cell, a pico cell, afemto cell, and/or another type of cell. A macro cell may cover arelatively large geographic area (e.g., several kilometers in radius)and may allow unrestricted access by UEs with service subscription. Apico cell may cover a relatively small geographic area and may allowunrestricted access by UEs with service subscription. A femto cell maycover a relatively small geographic area (e.g., a home) and may allowrestricted access by UEs having association with the femto cell (e.g.,UEs in a closed subscriber group (CSG)). A BS for a macro cell may bereferred to as a macro BS. A BS for a pico cell may be referred to as apico BS. A BS for a femto cell may be referred to as a femto BS or ahome BS. In the example shown in FIG. 1, a BS 110 a may be a macro BSfor a macro cell 102 a, a BS 110 b may be a pico BS for a pico cell 102b, and a BS 110 c may be a femto BS for a femto cell 102 c. A BS maysupport one or multiple (e.g., three) cells. The terms “eNB”, “basestation”, “NR BS”, “gNB”, “TRP”, “AP”, “node B”, “5G NB”, and “cell” maybe used interchangeably herein.

In some examples, a cell may not necessarily be stationary, and thegeographic area of the cell may move according to the location of amobile BS. In some examples, the BSs may be interconnected to oneanother and/or to one or more other BSs or network nodes (not shown) inthe access network 100 through various types of backhaul interfaces suchas a direct physical connection, a virtual network, and/or the likeusing any suitable transport network.

Wireless network 100 may also include relay stations. A relay station isan entity that can receive a transmission of data from an upstreamstation (e.g., a BS or a UE) and send a transmission of the data to adownstream station (e.g., a UE or a BS). A relay station may also be aUE that can relay transmissions for other UEs. In the example shown inFIG. 1, a relay station 110 d may communicate with macro BS 110 a and aUE 120 d in order to facilitate communication between BS 110 a and UE120 d. A relay station may also be referred to as a relay BS, a relaybase station, a relay, etc.

Wireless network 100 may be a heterogeneous network that includes BSs ofdifferent types, e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.These different types of BSs may have different transmit power levels,different coverage areas, and different impact on interference inwireless network 100. For example, macro BSs may have a high transmitpower level (e.g., 5 to 40 Watts) whereas pico BSs, femto BSs, and relayBSs may have lower transmit power levels (e.g., 0.1 to 2 Watts).

A network controller 130 may couple to a set of BSs and may providecoordination and control for these BSs. Network controller 130 maycommunicate with the BSs via a backhaul. The BSs may also communicatewith one another, e.g., directly or indirectly via a wireless orwireline backhaul.

UEs 120 (e.g., 120 a, 120 b, 120 c) may be dispersed throughout wirelessnetwork 100, and each UE may be stationary or mobile. A UE may also bereferred to as an access terminal, a terminal, a mobile station, asubscriber unit, a station, etc. A UE may be a cellular phone (e.g., asmart phone), a personal digital assistant (PDA), a wireless modem, awireless communication device, a handheld device, a laptop computer, acordless phone, a wireless local loop (WLL) station, a tablet, a camera,a gaming device, a netbook, a smartbook, an ultrabook, medical device orequipment, biometric sensors/devices, wearable devices (smart watches,smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g.,smart ring, smart bracelet)), an entertainment device (e.g., a music orvideo device, or a satellite radio), a vehicular component or sensor,smart meters/sensors, industrial manufacturing equipment, a globalpositioning system device, or any other suitable device that isconfigured to communicate via a wireless or wired medium.

Some UEs may be considered machine-type communication (MTC) or evolvedor enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEsinclude, for example, robots, drones, remote devices, such as sensors,meters, monitors, location tags, etc., that may communicate with a basestation, another device (e.g., remote device), or some other entity. Awireless node may provide, for example, connectivity for or to a network(e.g., a wide area network such as Internet or a cellular network) via awired or wireless communication link. Some UEs may be consideredInternet-of-Things (IoT) devices, and/or may be implemented as may beimplemented as NB-IoT (narrowband internet of things) devices. Some UEsmay be considered a Customer Premises Equipment (CPE). UE 120 may beincluded inside a housing that houses components of UE 120, such asprocessor components, memory components, and/or the like.

In general, any number of wireless networks may be deployed in a givengeographic area. Each wireless network may support a particular radioaccess technology (RAT) and may operate on one or more frequencies. ARAT may also be referred to as a radio technology, an air interface,etc. A frequency may also be referred to as a carrier, a frequencychannel, etc. Each frequency may support a single RAT in a givengeographic area in order to avoid interference between wireless networksof different RATs. In some cases, NR or 5G RAT networks may be deployed.

In some examples, access to the air interface may be scheduled, whereina scheduling entity (e.g., a base station) allocates resources forcommunication among some or all devices and equipment within thescheduling entity's service area or cell. Within the present disclosure,as discussed further below, the scheduling entity may be responsible forscheduling, assigning, reconfiguring, and releasing resources for one ormore subordinate entities. That is, for scheduled communication,subordinate entities utilize resources allocated by the schedulingentity. UEs may synchronize with a base station in the downlinkdirection based at least in part on synchronization signals transmittedby the base station, and may perform a random access procedure tosynchronize with the base station in the uplink direction.

Base stations are not the only entities that may function as ascheduling entity. That is, in some examples, a UE may function as ascheduling entity, scheduling resources for one or more subordinateentities (e.g., one or more other UEs). In this example, the UE isfunctioning as a scheduling entity, and other UEs utilize resourcesscheduled by the UE for wireless communication. A UE may function as ascheduling entity in a peer-to-peer (P2P) network, and/or in a meshnetwork. In a mesh network example, UEs may optionally communicatedirectly with one another in addition to communicating with thescheduling entity.

Thus, in a wireless communication network with a scheduled access totime-frequency resources and having a cellular configuration, a P2Pconfiguration, and a mesh configuration, a scheduling entity and one ormore subordinate entities may communicate utilizing the scheduledresources.

As indicated above, FIG. 1 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 1.

FIG. 2 shows a block diagram of a design of base station 110 and UE 120,which may be one of the base stations and one of the UEs in FIG. 1. Basestation 110 may be equipped with T antennas 234 a through 234 t, and UE120 may be equipped with R antennas 252 a through 252 r, where ingeneral T>1 and R>1.

At base station 110, a transmit processor 220 may receive data from adata source 212 for one or more UEs, select one or more modulation andcoding schemes (MCS) for each UE based at least in part on channelquality indicators (CQIs) received from the UE, process (e.g., encodeand modulate) the data for each UE based at least in part on the MCS(s)selected for the UE, and provide data symbols for all UEs. Transmitprocessor 220 may also process system information (e.g., for semi-staticresource partitioning information (SRPI), etc.) and control information(e.g., CQI requests, grants, upper layer signaling, etc.) and provideoverhead symbols and control symbols. Transmit processor 220 may alsogenerate reference symbols for reference signals (e.g., the CRS) andsynchronization signals (e.g., the primary synchronization signal (PSS)and secondary synchronization signal (SSS)). A transmit (TX)multiple-input multiple-output (MIMO) processor 230 may perform spatialprocessing (e.g., precoding) on the data symbols, the control symbols,the overhead symbols, and/or the reference symbols, if applicable, andmay provide T output symbol streams to T modulators (MODs) 232 a through232 t. Each modulator 232 may process a respective output symbol stream(e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator232 may further process (e.g., convert to analog, amplify, filter, andupconvert) the output sample stream to obtain a downlink signal. Tdownlink signals from modulators 232 a through 232 t may be transmittedvia T antennas 234 a through 234 t, respectively.

At UE 120, antennas 252 a through 252 r may receive the downlink signalsfrom base station 110 and/or other base stations and may providereceived signals to demodulators (DEMODs) 254 a through 254 r,respectively. Each demodulator 254 may condition (e.g., filter, amplify,downconvert, and digitize) a received signal to obtain input samples.Each demodulator 254 may further process the input samples (e.g., forOFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtainreceived symbols from all R demodulators 254 a through 254 r, performMIMO detection on the received symbols if applicable, and providedetected symbols. A receive processor 258 may process (e.g., demodulateand decode) the detected symbols, provide decoded data for UE 120 to adata sink 260, and provide decoded control information and systeminformation to a controller/processor 280. A channel processor maydetermine reference signal received power (RSRP), received signalstrength indicator (RSSI), reference signal received quality (RSRQ),channel quality indicator (CQI), etc.

On the uplink, at UE 120, a transmit processor 264 may receive andprocess data from a data source 262 and control information (e.g., forreports comprising RSRP, RSSI, RSRQ, CQI, etc.) fromcontroller/processor 280. Transmit processor 264 may also generatereference symbols for one or more reference signals. The symbols fromtransmit processor 264 may be precoded by a TX MIMO processor 266 ifapplicable, further processed by modulators 254 a through 254 r (e.g.,for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to base station 110. Insome aspects, the UE 120 may transmit a random access preamble to thebase station 110. At base station 110, the uplink signals from UE 120and other UEs may be received by antennas 234, processed by demodulators232, detected by a MIMO detector 236 if applicable, and furtherprocessed by a receive processor 238 to obtain decoded data and controlinformation sent by UE 120. Receive processor 238 may provide thedecoded data to a data sink 239 and the decoded control information tocontroller/processor 240. In some aspects, base station 110 may providea random access response based at least in part on a random accesspreamble received from the UE 120. The random access response mayidentify characteristics of a radio resource control connection setupmessage and/or the like. Base station 110 may include communication unit244 and communicate to network controller 130 via communication unit244. Network controller 130 may include communication unit 294,controller/processor 290, and memory 292.

In some aspects, one or more components of UE 120 may be included in ahousing. Controllers/processors 240 and 280 and/or any othercomponent(s) in FIG. 2 may direct the operation at base station 110 andUE 120, respectively, to perform supplementary uplink random accessconfiguration. For example, controller/processor 280 and/or otherprocessors and modules at UE 120, may perform or direct operations of UE120 to perform supplementary uplink random access configuration. Forexample, controller/processor 280 and/or other controllers/processorsand modules at UE 120 may perform or direct operations of, for example,process 1000 of FIG. 10 and/or other processes as described herein. Insome aspects, one or more of the components shown in FIG. 2 may beemployed to perform example process 1000 and/or other processes for thetechniques described herein. Memories 242 and 282 may store data andprogram codes for base station 110 and UE 120, respectively. A scheduler246 may schedule UEs for data transmission on the downlink and/oruplink.

In some aspects, UE 120 may include means for receiving random accesschannel (RACH) configuration information on a downlink carrier of afirst set of carriers, means for selectively performing a RACH procedurewith regard to the first set of carriers or the second set of carriersbased at least in part on the RACH configuration information, and/or thelike. In some aspects, such means may include one or more components ofUE 120 described in connection with FIG. 2.

As indicated above, FIG. 2 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 2.

FIG. 3 shows an example frame structure 300 for frequency divisionduplexing (FDD) in a telecommunications system (e.g., LTE). Thetransmission timeline for each of the downlink and uplink may bepartitioned into units of radio frames. Each radio frame may have apredetermined duration (e.g., 10 milliseconds (ms)) and may bepartitioned into 10 subframes with indices of 0 through 9. Each subframemay include two slots. Each radio frame may thus include 20 slots withindices of 0 through 19. Each slot may include L symbol periods, e.g.,seven symbol periods for a normal cyclic prefix (as shown in FIG. 3) orsix symbol periods for an extended cyclic prefix. The 2L symbol periodsin each subframe may be assigned indices of 0 through 2L−1.

While some techniques are described herein in connection with frames,subframes, slots, and/or the like, these techniques may equally apply toother types of wireless communication structures, which may be referredto using terms other than “frame,” “subframe,” “slot,” and/or the likein 5G NR. In some aspects, a wireless communication structure may referto a periodic time-bounded communication unit defined by a wirelesscommunication standard and/or protocol.

In certain telecommunications (e.g., LTE), a BS may transmit a primarysynchronization signal (PSS) and a secondary synchronization signal(SSS) on the downlink in the center of the system bandwidth for eachcell supported by the BS. The PSS and SSS may be transmitted in symbolperiods 6 and 5, respectively, in subframes 0 and 5 of each radio framewith the normal cyclic prefix, as shown in FIG. 3. The PSS and SSS maybe used by UEs for cell search and acquisition. The BS may transmit acell-specific reference signal (CRS) across the system bandwidth foreach cell supported by the BS. The CRS may be transmitted in certainsymbol periods of each subframe and may be used by the UEs to performchannel estimation, channel quality measurement, and/or other functions.The BS may also transmit a physical broadcast channel (PBCH) in symbolperiods 0 to 3 in slot 1 of certain radio frames. The PBCH may carrysome system information. The BS may transmit other system informationsuch as system information blocks (SIBs) on a physical downlink sharedchannel (PDSCH) in certain subframes. The BS may transmit controlinformation/data on a physical downlink control channel (PDCCH) in thefirst B symbol periods of a subframe, where B may be configurable foreach subframe. The BS may transmit traffic data and/or other data on thePDSCH in the remaining symbol periods of each subframe.

In other systems (e.g., such NR or 5G systems), a Node B may transmitthese or other signals in these locations or in different locations ofthe subframe.

As indicated above, FIG. 3 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 3.

FIG. 4 shows two example subframe formats 410 and 420 with the normalcyclic prefix. The available time frequency resources may be partitionedinto resource blocks. Each resource block may cover 12 subcarriers inone slot and may include a number of resource elements. Each resourceelement may cover one subcarrier in one symbol period and may be used tosend one modulation symbol, which may be a real or complex value.

Subframe format 410 may be used for two antennas. A CRS may betransmitted from antennas 0 and 1 in symbol periods 0, 4, 7, and 11. Areference signal is a signal that is known a priori by a transmitter anda receiver and may also be referred to as a pilot signal. A CRS is areference signal that is specific for a cell, e.g., generated based atleast in part on a cell identity (ID). In FIG. 4, for a given resourceelement with label Ra, a modulation symbol may be transmitted on thatresource element from antenna a, and no modulation symbols may betransmitted on that resource element from other antennas. Subframeformat 420 may be used with four antennas. A CRS may be transmitted fromantennas 0 and 1 in symbol periods 0, 4, 7, and 11 and from antennas 2and 3 in symbol periods 1 and 8. For both subframe formats 410 and 420,a CRS may be transmitted on evenly spaced subcarriers, which may bedetermined based at least in part on cell ID. CRSs may be transmitted onthe same or different subcarriers, depending on their cell IDs. For bothsubframe formats 410 and 420, resource elements not used for the CRS maybe used to transmit data (e.g., traffic data, control data, and/or otherdata).

The PSS, SSS, CRS and PBCH in LTE are described in 3GPP TechnicalSpecification 36.211, entitled “Evolved Universal Terrestrial RadioAccess (E-UTRA); Physical Channels and Modulation,” which is publiclyavailable.

An interlace structure may be used for each of the downlink and uplinkfor FDD in certain telecommunications systems (e.g., LTE). For example,Q interlaces with indices of 0 through Q−1 may be defined, where Q maybe equal to 4, 6, 8, 10, or some other value. Each interlace may includesubframes that are spaced apart by Q frames. In particular, interlace qmay include subframes q, q+Q, q+2Q, etc., where q∈{0, . . . , Q−1}.

The wireless network may support hybrid automatic retransmission request(HARQ) for data transmission on the downlink and uplink. For HARQ, atransmitter (e.g., a BS) may send one or more transmissions of a packetuntil the packet is decoded correctly by a receiver (e.g., a UE) or someother termination condition is encountered. For synchronous HARQ, alltransmissions of the packet may be sent in subframes of a singleinterlace. For asynchronous HARQ, each transmission of the packet may besent in any subframe.

A UE may be located within the coverage of multiple BSs. One of theseBSs may be selected to serve the UE. The serving BS may be selectedbased at least in part on various criteria such as received signalstrength, received signal quality, path loss, and/or the like. Receivedsignal quality may be quantified by a signal-to-noise-and-interferenceratio (SINR), or a reference signal received quality (RSRQ), or someother metric. The UE may operate in a dominant interference scenario inwhich the UE may observe high interference from one or more interferingBSs.

While aspects of the examples described herein may be associated withLTE technologies, aspects of the present disclosure may be applicablewith other wireless communication systems, such as NR or 5Gtechnologies.

New radio (NR) may refer to radios configured to operate according to anew air interface (e.g., other than Orthogonal Frequency DivisionalMultiple Access (OFDMA)-based air interfaces) or fixed transport layer(e.g., other than Internet Protocol (IP)). In aspects, NR may utilizeOFDM with a CP (herein referred to as cyclic prefix OFDM or CP-OFDM)and/or SC-FDM on the uplink, may utilize CP-OFDM on the downlink andinclude support for half-duplex operation using time division duplexing(TDD). In aspects, NR may, for example, utilize OFDM with a CP (hereinreferred to as CP-OFDM) and/or discrete Fourier transform spreadorthogonal frequency-division multiplexing (DFT-s-OFDM) on the uplink,may utilize CP-OFDM on the downlink and include support for half-duplexoperation using TDD. NR may include Enhanced Mobile Broadband (eMBB)service targeting wide bandwidth (e.g., 80 megahertz (MHz) and beyond),millimeter wave (mmW) targeting high carrier frequency (e.g., 60gigahertz (GHz)), massive MTC (mMTC) targeting non-backward compatibleMTC techniques, and/or mission critical targeting ultra reliable lowlatency communications (URLLC) service.

A single component carrier bandwidth of 100 MHZ may be supported. NRresource blocks may span 12 sub-carriers with a sub-carrier bandwidth of75 kilohertz (kHz) over a 0.1 ms duration. Each radio frame may include50 subframes with a length of 10 ms. Consequently, each subframe mayhave a length of 0.2 ms. Each subframe may indicate a link direction(e.g., DL or UL) for data transmission and the link direction for eachsubframe may be dynamically switched. Each subframe may include DL/ULdata as well as DL/UL control data. UL and DL subframes for NR may be asdescribed in more detail below with respect to FIGS. 7 and 8.

Beamforming may be supported and beam direction may be dynamicallyconfigured. MIMO transmissions with precoding may also be supported.MIMO configurations in the DL may support up to 8 transmit antennas withmulti-layer DL transmissions up to 8 streams and up to 2 streams per UE.Multi-layer transmissions with up to 2 streams per UE may be supported.Aggregation of multiple cells may be supported with up to 8 servingcells. Alternatively, NR may support a different air interface, otherthan an OFDM-based interface. NR networks may include entities suchcentral units or distributed units.

The RAN may include a central unit (CU) and distributed units (DUs). ANR BS (e.g., gNB, 5G Node B, Node B, transmit receive point (TRP),access point (AP)) may correspond to one or multiple BSs. NR cells canbe configured as access cells (ACells) or data only cells (DCells). Forexample, the RAN (e.g., a central unit or distributed unit) canconfigure the cells. DCells may be cells used for carrier aggregation ordual connectivity, but not used for initial access, cellselection/reselection, or handover. In some cases, DCells may nottransmit synchronization signals. In some cases, DCells may transmitsynchronization signals. NR BSs may transmit downlink signals to UEsindicating the cell type. Based at least in part on the cell typeindication, the UE may communicate with the NR BS. For example, the UEmay determine NR BSs to consider for cell selection, access, handover,and/or measurement based at least in part on the indicated cell type.

As indicated above, FIG. 4 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 4.

FIG. 5 illustrates an example logical architecture of a distributed RAN500, according to aspects of the present disclosure. A 5G access node506 may include an access node controller (ANC) 502. The ANC may be acentral unit (CU) of the distributed RAN 500. The backhaul interface tothe next generation core network (NG-CN) 504 may terminate at the ANC.The backhaul interface to neighboring next generation access nodes(NG-ANs) may terminate at the ANC. The ANC may include one or more TRPs508 (which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs,gNB, or some other term). As described above, a TRP may be usedinterchangeably with “cell.”

The TRPs 508 may be a distributed unit (DU). The TRPs may be connectedto one ANC (ANC 502) or more than one ANC (not illustrated). Forexample, for RAN sharing, radio as a service (RaaS), and servicespecific AND deployments, the TRP may be connected to more than one ANC.A TRP may include one or more antenna ports. The TRPs may be configuredto individually (e.g., dynamic selection) or jointly (e.g., jointtransmission) serve traffic to a UE.

The local architecture of RAN 500 may be used to illustrate fronthauldefinition. The architecture may be defined that support fronthaulingsolutions across different deployment types. For example, thearchitecture may be based at least in part on transmit networkcapabilities (e.g., bandwidth, latency, and/or jitter).

The architecture may share features and/or components with LTE.According to aspects, the next generation AN (NG-AN) 510 may supportdual connectivity with NR. The NG-AN may share a common fronthaul forLTE and NR.

The architecture may enable cooperation between and among TRPs 508. Forexample, cooperation may be preset within a TRP and/or across TRPs viathe ANC 502. According to aspects, no inter-TRP interface may beneeded/present.

According to aspects, a dynamic configuration of split logical functionsmay be present within the architecture of RAN 500. The packet dataconvergence protocol (PDCP), radio link control (RLC), media accesscontrol (MAC) protocol may be adaptably placed at the ANC or TRP.

According to certain aspects, a BS may include a central unit (CU)(e.g., ANC 502) and/or one or more distributed units (e.g., one or moreTRPs 508).

As indicated above, FIG. 5 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 5.

FIG. 6 illustrates an example physical architecture of a distributed RAN600, according to aspects of the present disclosure. A centralized corenetwork unit (C-CU) 602 may host core network functions. The C-CU may becentrally deployed. C-CU functionality may be offloaded (e.g., toadvanced wireless services (AWS)), in an effort to handle peak capacity.

A centralized RAN unit (C-RU) 604 may host one or more ANC functions.Optionally, the C-RU may host core network functions locally. The C-RUmay have distributed deployment. The C-RU may be closer to the networkedge.

A distributed unit (DU) 606 may host one or more TRPs. The DU may belocated at edges of the network with radio frequency (RF) functionality.

As indicated above, FIG. 6 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 6.

FIG. 7 is a diagram 700 showing an example of a DL-centric subframe orwireless communication structure. The DL-centric subframe may include acontrol portion 702. The control portion 702 may exist in the initial orbeginning portion of the DL-centric subframe. The control portion 702may include various scheduling information and/or control informationcorresponding to various portions of the DL-centric subframe. In someconfigurations, the control portion 702 may be a physical DL controlchannel (PDCCH), as indicated in FIG. 7. In some aspects, the controlportion may include RACH configuration information for a UE 120. In someaspects, the control portion 702 may include legacy PDCCH information,shortened PDCCH (sPDCCH) information), a control format indicator (CFI)value (e.g., carried on a physical control format indicator channel(PCFICH)), one or more grants (e.g., downlink grants, uplink grants,etc.), and/or the like.

The DL-centric subframe may also include a DL data portion 704. The DLdata portion 704 may sometimes be referred to as the payload of theDL-centric subframe. The DL data portion 704 may include thecommunication resources utilized to communicate DL data from thescheduling entity (e.g., UE or BS) to the subordinate entity (e.g., UE).In some configurations, the DL data portion 704 may be a physical DLshared channel (PDSCH).

The DL-centric subframe may also include an UL short burst portion 706.The UL short burst portion 706 may sometimes be referred to as an ULburst, an UL burst portion, a common UL burst, a short burst, an ULshort burst, a common UL short burst, a common UL short burst portion,and/or various other suitable terms. In some aspects, the UL short burstportion 706 may include a random access preamble or the like. In someaspects, the UL short burst portion 706 may include one or morereference signals. Additionally, or alternatively, the UL short burstportion 706 may include feedback information corresponding to variousother portions of the DL-centric subframe. For example, the UL shortburst portion 706 may include feedback information corresponding to thecontrol portion 702 and/or the data portion 704. Non-limiting examplesof information that may be included in the UL short burst portion 706include an acknowledgment (ACK) signal (e.g., a physical uplink controlchannel (PUCCH) ACK, a physical uplink shared channel (PUSCH) ACK, animmediate ACK), a non-acknowledgment (NACK) signal (e.g., a PUCCH NACK,a PUSCH NACK, an immediate NACK), a scheduling request (SR), a bufferstatus report (BSR), a HARQ indicator, a channel state indication (CSI),a channel quality indicator (CQI), a sounding reference signal (SRS), ademodulation reference signal (DMRS), PUSCH data, and/or various othersuitable types of information. The UL short burst portion 706 mayinclude additional or alternative information, such as informationpertaining to random access channel (RACH) procedures, schedulingrequests, and various other suitable types of information.

As illustrated in FIG. 7, the end of the DL data portion 704 may beseparated in time from the beginning of the UL short burst portion 706.This time separation may sometimes be referred to as a gap, a guardperiod, a guard interval, and/or various other suitable terms. Thisseparation provides time for the switch-over from DL communication(e.g., reception operation by the subordinate entity (e.g., UE)) to ULcommunication (e.g., transmission by the subordinate entity (e.g., UE)).The foregoing is merely one example of a DL-centric wirelesscommunication structure, and alternative structures having similarfeatures may exist without necessarily deviating from the aspectsdescribed herein.

As indicated above, FIG. 7 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 7.

FIG. 8 is a diagram 800 showing an example of an UL-centric subframe orwireless communication structure. The UL-centric subframe may include acontrol portion 802. The control portion 802 may exist in the initial orbeginning portion of the UL-centric subframe. The control portion 802 inFIG. 8 may be similar to the control portion 702 described above withreference to FIG. 7. The UL-centric subframe may also include an UL longburst portion 804. The UL long burst portion 804 may sometimes bereferred to as the payload of the UL-centric subframe. The UL portionmay refer to the communication resources utilized to communicate UL datafrom the subordinate entity (e.g., UE) to the scheduling entity (e.g.,UE or BS). In some configurations, the control portion 802 may be aphysical DL control channel (PDCCH).

As illustrated in FIG. 8, the end of the control portion 802 may beseparated in time from the beginning of the UL long burst portion 804.This time separation may sometimes be referred to as a gap, guardperiod, guard interval, and/or various other suitable terms. Thisseparation provides time for the switch-over from DL communication(e.g., reception operation by the scheduling entity) to UL communication(e.g., transmission by the scheduling entity).

The UL-centric subframe may also include an UL short burst portion 806.The UL short burst portion 806 in FIG. 8 may be similar to the UL shortburst portion 706 described above with reference to FIG. 7, and mayinclude any of the information described above in connection with FIG.7. The foregoing is merely one example of an UL-centric wirelesscommunication structure, and alternative structures having similarfeatures may exist without necessarily deviating from the aspectsdescribed herein.

In some circumstances, two or more subordinate entities (e.g., UEs) maycommunicate with each other using sidelink signals. Real-worldapplications of such sidelink communications may include public safety,proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V)communications, Internet of Everything (IoE) communications, IoTcommunications, mission-critical mesh, and/or various other suitableapplications. Generally, a sidelink signal may refer to a signalcommunicated from one subordinate entity (e.g., UE1) to anothersubordinate entity (e.g., UE2) without relaying that communicationthrough the scheduling entity (e.g., UE or BS), even though thescheduling entity may be utilized for scheduling and/or controlpurposes. In some examples, the sidelink signals may be communicatedusing a licensed spectrum (unlike wireless local area networks, whichtypically use an unlicensed spectrum).

In one example, a wireless communication structure, such as a frame, mayinclude both UL-centric subframes and DL-centric subframes. In thisexample, the ratio of UL-centric subframes to DL-centric subframes in aframe may be dynamically adjusted based at least in part on the amountof UL data and the amount of DL data that are transmitted. For example,if there is more UL data, then the ratio of UL-centric subframes toDL-centric subframes may be increased. Conversely, if there is more DLdata, then the ratio of UL-centric subframes to DL-centric subframes maybe decreased.

As indicated above, FIG. 8 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 8.

FIGS. 9A-9E are diagrams illustrating examples 900 of supplementaryuplink random access configuration, in accordance with various aspectsof the present disclosure.

FIG. 9A shows an example of configuring a RACH procedure for asupplementary uplink carrier using RACH configuration informationprovided on a different set of carriers than one including thesupplementary uplink carrier. As shown in FIG. 9A, and by referencenumber 902, a BS 110 may provide RACH configuration information to a UE120 on a downlink carrier of a high band (i.e., a higher frequency bandthan a low band). For example, the downlink carrier may be included in afirst set of carriers in the high band. As further shown, the RACHconfiguration information may include configuration information for alluplink carriers of the UE 120. For example, the RACH configurationinformation may pertain to the first set of carriers and to a second setof carriers on the low band (e.g., a lower frequency band than the highband) that includes a supplementary uplink carrier of the UE 120. Insome aspects, the RACH configuration information may include, forexample, a threshold (e.g., an RSRP threshold and/or the like) forselection of a synchronization signal block for the first set ofcarriers, a threshold for selection of a synchronization signal blockfor the second set of carriers, a starting index of a random accesspreamble group for the first set of carriers and/or the second set ofcarriers, a number of random access preambles for the first set ofcarriers and/or the second set of carriers, a configured UE transmittedpower of the supplementary uplink carrier, a configured UE transmittedpower of the downlink carrier and/or a serving cell of the high band(e.g., the cell performing the random access procedure), and/or thelike.

As shown by reference number 904, the UE 120 may determine to perform aRACH procedure using the supplementary uplink carrier associated with alowest-frequency band. For example, the UE 120 may determine to performthe RACH procedure using the RACH configuration information for a lowestfrequency band supported by the UE 120. As another example, when the UE120 only supports a first set of carriers, the UE 120 may perform theRACH procedure using the first set of carriers and using the RACHconfiguration information for the first set of carriers. When the UE 120supports the first set of carriers and the second set of carriers, theUE 120 may perform the RACH procedure using a set of carriers associatedwith a lowest frequency band, of the first set of carriers and thesecond set of carriers, and may use corresponding RACH configurationinformation of the set of carriers associated with the lowest frequencyband. In some aspects, performing the RACH procedure may includeselecting a carrier, of the first set of carriers and the second set ofcarriers, and setting a transmission power to a configured UEtransmitted power for the selected carrier.

As shown by reference number 906, the UE 120 may transmit RACH procedureuplink traffic (e.g., the first message and/or the third message of theRACH procedure) using the second set of carriers (e.g., thesupplementary uplink carrier). In this way, the UE 120 may perform theRACH procedure using the second set of carriers, which improves uplinkperformance of the RACH procedure and which improves versatility of theUE 120.

As shown by reference number 908, in some aspects, the UE 120 mayreceive RACH procedure downlink traffic (e.g., the second message and/orthe fourth message of the RACH procedure) using the first set ofcarriers (e.g., the downlink carrier used to provide the RACHconfiguration information). As further shown, the UE 120 may optionallyreceive the RACH procedure downlink traffic using the second set ofcarriers (e.g., a paired downlink carrier of the supplementary uplinkcarrier). For example, when the supplementary uplink carrier isassociated with a paired downlink carrier, the BS 110 may provide theRACH procedure downlink traffic on the paired downlink carrier, therebyconserving resources of the downlink carrier of the first set ofcarriers. In some aspects, the UE 120 may modify or interpret the secondmessage differently based at least in part on whether the second messageis received using the first set of carriers or the second set ofcarriers, as described in more detail below. In some aspects, the UE 120may modify or interpret the second message differently based at least inpart on whether the second message is received using the primary uplinkor the supplementary uplink, as described in more detail elsewhereherein.

In some aspects, the UE 120 may determine whether the RACH procedure isto be performed using the first set of carriers or the second set ofcarriers based at least in part on a threshold. For example, the BS 110(or the UE 120) may configure a threshold, and the UE 120 mayselectively perform the RACH procedure using the first set of carriers,or the second set of carriers, based at least in part on whetherthreshold is satisfied. In some aspects, the threshold may be configuredto improve load balancing of the first set of carriers and the secondset of carriers. For example, the threshold may be based at least inpart on a function (e.g., a hash function) of a UE identifier of the UE120 (e.g., UEs 120 with an odd last digit may use the first set ofcarriers, and UEs 120 with an even last digit may use the second set ofcarriers).

In some aspects, the BS 110 may be capable of overriding the threshold.For example, the UE 120 may receive a flag, a value, and/or the likefrom the BS 110 indicating that the threshold is to be overridden. Insuch a case, the UE 120 may perform the RACH procedure using aparticular set of carriers, of the first set of carriers and the secondset of carriers, irrespective of a value associated with the threshold.For example, the particular set of carriers may be based at least inpart on a predefined setting of the UE 120, information specified by theflag or value received from the BS 110, a set of carriers associatedwith a lowest frequency, and/or the like.

FIG. 9B shows an example of falling back to a supplementary uplinkcarrier for transmission of a random access preamble. As shown in FIG.9B, and by reference number 910, in some aspects, the UE 120 may attemptto transmit a first message (e.g., a random access preamble, shown asMSG1) of the RACH procedure on the high band (e.g., the primary uplinkcarrier associated with the first set of carriers), and may beunsuccessful. For example, the high band may be more crowded than thelow band, or the UE 120 may experience more severe coupling loss at thehigh band than at the low band.

As shown by reference number 912, the UE 120 may determine thattransmission of the first message was unsuccessful on the primary uplinkcarrier and/or the high band. In some aspects, the UE 120 may determinethat the transmission of the first message was unsuccessful a particularnumber of times (e.g., three times, five times, and/or the like). Asfurther shown, the UE 120 may determine that the first message is to beretransmitted on the supplementary uplink carrier (e.g., the carrierassociated with the low band).

As shown by reference number 914, the UE 120 may transmit the firstmessage on the low band using the supplementary uplink carrier. In thisway, the UE 120 may fall back to a supplementary uplink carrier for theRACH procedure when performance of the RACH procedure on the primaryuplink carrier is unsuccessful.

As further shown, in some aspects, the UE 120 may reinitiate open looppower control for the first message on the low band. For example, the UE120 may start transmission of the first message at a first power level,and may incrementally increase the power level when the transmission isunsuccessful, which may improve battery performance of the UE 120.Additionally, or alternatively, the UE 120 may reuse the power levelused to transmit the first message on the primary uplink carrier, whichmay conserve resources of the UE 120 that would be used to perform openloop power control, and which may improve the likelihood of successfultransmission of the first message.

FIG. 9C shows an example of interpreting a random access response and/ora TPC command based at least in part on a configuration to transmit aparticular message (e.g., an RRC connection setup message) on asupplementary uplink carrier. As shown in FIG. 9C, and by referencenumber 916, the BS 110 may transmit a second message (e.g., shown asMSG2) to the UE 120 on the downlink carrier associated with the firstset of carriers as part of the RACH procedure. In some aspects, thesecond message may include a random access response, and/or the like. Asfurther shown, the second message may include a TPC command. The TPCcommand may identify a power back-off for transmission of a thirdmessage by the UE 120. However, the power level used for transmission onthe primary uplink carrier may be different than the power level usedfor transmission on the supplementary uplink carrier due to differencesin coupling loss, channel characteristics, and/or the like. Furthermore,it may be beneficial to use different waveforms (e.g., DFT-spreadwaveforms versus CP-OFDM waveforms) for the supplementary uplink carrierand the primary uplink carrier. Still further, it may be beneficial touse a different numerology (e.g., subcarrier spacing, etc.) for thesupplementary uplink carrier and the primary uplink carrier. In someaspects, the second message may identify a waveform and/or numerologyfor transmission of the third message.

As shown by reference number 918, the UE 120 may determine that thethird message is to be transmitted on the supplementary uplink carrierassociated with the second set of carriers. Therefore, the UE 120 mayinterpret the second message differently than if the third message is tobe transmitted on the primary uplink carrier. For example, the UE 120may determine to use at least one of a modified TPC power offset (e.g.,a modified power level or power back-off), a modified waveform, and/or amodified numerology to transmit the third message on the supplementaryuplink carrier in comparison to transmitting the third message on theprimary uplink carrier. For example, the UE 120 may use a lower powerlevel (e.g., a higher TPC power offset or power back-off), may use asimpler waveform (e.g., a CP-OFDM waveform), and/or may use a tightersubcarrier spacing for the transmission of the third message using thesupplementary uplink carrier in comparison to transmitting the thirdmessage on the primary uplink carrier.

In some instances as used herein, the term “interpret” may includeperforming, by the UE 120 for example, a determination or reading ofinformation based on at least one factor in addition to the content of amessage. In the present example, the UE 120 may receive a second messagewhose contents include parameters to be used by the UE 120 fortransmission of a subsequent third message. The parameters, asdetermined by the UE 120, however, may differ depending on whether thethird message is to be transmitted on a primary uplink carrier or on asupplementary uplink carrier, although the content of the second messageas received by the UE 120 remains the same. For example, the UE 120 maydetermine that the contents of the second message indicate a first setof parameters for transmission of the third message if the UE 120 isconfigured to transmit the third message on a primary uplink carrier,while the UE 120 may determine that the contents of the second messageindicate a second set of parameters for transmission of the thirdmessage if the UE 120 is configured to transmit the third message on asupplementary uplink carrier. In some instances, a processor 280 of theUE 120 may perform the interpreting, determining, or reading of thesecond message.

As shown by reference number 920, the UE 120 may transmit the thirdmessage of the RACH procedure on the supplementary uplink carrierassociated with the low band. As shown, in some aspects, the UE 120 maytransmit the third message at diminished transmission power.Additionally, or alternatively, the UE 120 may transmit the thirdmessage with a modified waveform. Additionally, or alternatively, the UE120 may transmit the third message with a modified numerology. In thisway, transmission performance of the UE 120 with regard to the thirdmessage may be improved. Furthermore, the specified transmission powercan be adjusted for the supplementary uplink carrier, which may enablemore reliable operation of the RACH procedure and/or reduce batteryconsumption associated with the RACH procedure.

FIG. 9D shows an example of generating a grant for a third message(e.g., an RRC connection setup message) based at least in part onreceiving a first message (e.g., a random access preamble) on asupplementary uplink carrier. As shown in FIG. 9D, and by referencenumber 922, the BS 110 may determine that the UE 120 is performing theRACH procedure using the supplementary uplink carrier (e.g., the secondset of carriers) according to the first message (e.g., based at least inpart on the first message being received on the second set of carriers).As further shown, the BS 110 may determine that a resource allocationand/or a TPC command of a grant (e.g., a grant provided using the secondmessage of the RACH procedure) are to be formatted for the supplementaryuplink carrier. For example, the supplementary uplink carrier may use adifferent resource allocation format, a different TPC command format,and/or the like than the primary uplink carrier. By using the differentresource allocation format, the different TPC command format, and/or thelike, the BS 110 may improve versatility of the RACH procedure and mayenable performance of the RACH procedure using the supplementary uplinkcarrier.

In some aspects, the TPC command may have a different width fordifferent frequency bands. For example, the TPC command may have anarrower width (e.g., 3 bits) for a frequency band associated with LTE,and may have a wider width (e.g., greater than 3 bits) for a 5G or NRband. In some aspects, the second message may exclude a channel qualityindicator (CQI) request bit when the third message is to be provided onthe supplementary uplink channel. For example, when the supplementaryuplink channel is not associated with a paired downlink channel, a CQImay not be beneficial. Therefore, the BS 110 may omit the CQI requestbit from the grant.

In some aspects, the resource allocation scheme may be different whenthe third message is to be provided on the supplementary uplink carrier.For example, the BS 110 may use a different subcarrier spacing, mayallocate resources of a different uplink bandwidth, and/or the like.

As shown by reference number 924, the BS 110 may provide the secondmessage of the RACH procedure (e.g., the random access response),including the grant for the third message, on a downlink carrier of thefirst set of carriers (e.g., associated with the higher frequency bandof the UE 120). As shown by reference number 926, the UE 120 maydetermine to transmit the third message on the supplementary uplinkcarrier according to the information included in the grant, and, asshown by reference number 928, the UE 120 may transmit the third messageon the supplementary uplink carrier. By transmitting the third messageaccording to the information included in the grant, the UE 120 mayimprove RACH procedure performance on the supplementary uplink carrier.

FIG. 9E is an example of generating a random access radio networktemporary identifier including a carrier frequency offset index. Asshown in FIG. 9E, and by reference number 930, the BS 110 may generate arandom access radio network temporary identifier (RA-RNTI) for the UE120. The BS 110 may generate the RA-RNTI using information provided bythe UE 120 (e.g., a slot index for the slot on which the UE 120 providedthe first message and a carrier frequency offset index for the carrieron which the UE 120 provided the first message). The RA-RNTI may be usedto scramble a PDCCH grant for PDSCH resources on which to provide thesecond message of the RACH procedure. In some aspects, the BS 110 maygenerate the RA-RNTI using an uplink carrier identifier based at leastin part on whether the first set of carriers or the second set ofcarriers is used for the RACH procedure. For example, the uplink carrieridentifier may have a first value when the first set of carriers is usedand may have a second value when a second set of carriers is used.

By generating the RA-RNTI using the carrier frequency offset index,provision of an RA-RNTI on a downlink carrier for a different set ofcarriers than the supplementary uplink carrier is enabled. For example,a traditional RA-RNTI may be generated using the slot index and not thecarrier frequency offset. In such a situation, when the UE 120 receivesthe PDCCH with the grant for the random access response, the UE 120 maynot be able to identify the uplink carrier on which the random accesspreamble (e.g., the first message) was provided. By generating theRA-RNTI using the carrier frequency offset index, provision of therandom access response on a different set of carriers than the randomaccess preamble is enabled.

As shown by reference number 932, the UE 120 may receive the grant forthe second message (e.g., the random access response). As further shown,the grant may be scrambled using the RA-RNTI (e.g., that identifies thecarrier frequency offset index), and may be received on the downlinkcarrier associated with the first set of carriers.

As shown by reference number 934, the UE 120 may unscramble the grantusing the slot index and carrier frequency offset index from the firstmessage (e.g., the random access preamble). For example, the UE 120 mayknow the slot index and the carrier frequency offset index, and mayattempt to unscramble the grant using the known slot index and thecarrier frequency offset index. Since unscrambling in such a case issuccessful, the UE 120 may determine that the granted resources are forthe UE 120, and may receive the second message (e.g., the random accessresponse) on the granted resources.

As shown by reference number 936, the BS 110 may provide the secondmessage (e.g., the random access response) on the granted resourcesusing the downlink carrier of the first set of carriers. As shown byreference number 938, the UE 120 may receive the second message (e.g.,the random access response) on the granted resources, and may performthe RACH procedure accordingly, as described in more detail elsewhereherein. Thus, the RA-RNTI is determined based at least in part on acarrier frequency offset index, which enables provision of the randomaccess preamble on a different carrier than the grant for the randomaccess response.

In some aspects, the grant and/or the random access response may includeinformation identifying the carrier on which the random access preamblewas received (e.g., the supplementary uplink carrier). For example, suchinformation may be included in a payload of the grant and/or the randomaccess response. Thus, complexity of generating the RA-RNTI is reduced.

As indicated above, FIGS. 9A-9E are provided as examples. Other examplesare possible and may differ from what was described with respect toFIGS. 9A-9E.

FIG. 10 is a diagram illustrating an example process 1000 performed, forexample, by a UE, in accordance with various aspects of the presentdisclosure. Example process 1000 is an example where a UE (e.g., UE 120)performs supplementary uplink random access configuration.

As shown in FIG. 10, in some aspects, process 1000 may include receivingrandom access channel (RACH) configuration information on a downlinkcarrier of a first set of carriers, wherein the RACH configurationinformation pertains to the first set of carriers and to a second set ofcarriers (block 1010). For example, the UE (e.g., using antenna 252,DEMOD 254, MIMO detector 256, receive processor 258,controller/processor 280, and/or the like) may receive RACHconfiguration information on a downlink carrier of a first set ofcarriers. The RACH configuration information may pertain to the firstset of carriers and to a second set of carriers.

As further shown in FIG. 10, in some aspects, process 1000 may includeselectively performing a RACH procedure with regard to the first set ofcarriers or the second set of carriers based at least in part on theRACH configuration information (block 1020). For example, the UE (e.g.,using controller/processor 280 and/or the like) may selectively performa RACH procedure with regard to the first set of carriers or the secondset of carriers. When the UE performs the RACH procedure with regard tothe first set of carriers, the UE may use RACH configuration informationpertaining to the first set of carriers. When the UE performs the RACHprocedure with regard to the second set of carriers, the UE may use RACHconfiguration information pertaining to the second set of carriers.

Process 1000 may include additional aspects, such as any single aspector any combination of aspects described below and/or in connection withone or more other processes described elsewhere herein.

In some aspects, the first set of carriers is associated with a higherfrequency band than the second set of carriers. In some aspects, thesecond set of carriers includes an uplink carrier that is asupplementary uplink carrier of the user equipment. In some aspects, theRACH configuration information is received in system information orradio resource control configuration information of the user equipment.

In some aspects, the user equipment is configured to perform the RACHprocedure with regard to a particular set of carriers, of the first setof carriers and the second set of carriers, associated with a lowestfrequency band supported by the user equipment. In some aspects, theRACH procedure is performed with regard to the particular set ofcarriers using information, of the RACH configuration information, thatis pertinent to the particular set of carriers. In some aspects, theuser equipment is configured to select a particular set of carriers, ofthe first set of carriers and the second set of carriers, to use toperform the RACH procedure based at least in part on a threshold. Insome aspects, the threshold is configured to balance a load, relating tothe RACH procedure, between the first set of carriers and the second setof carriers.

In some aspects, the threshold is based at least in part on a hashfunction performed using an identifier associated with the userequipment. In some aspects, the user equipment is configured to performthe RACH procedure with regard to a particular set of carriers, of thefirst set of carriers and the second set of carriers, based at least inpart on a flag or value received by the user equipment and indicating toperform the RACH procedure with regard to the particular set ofcarriers. In some aspects, selectively performing the RACH procedurecomprises retransmitting a first message of the RACH procedure on thesecond set of carriers based at least in part on an unsuccessfultransmission of the first message on the first set of carriers. In someaspects, the first message is retransmitted on the second set ofcarriers based at least in part on a particular number of unsuccessfultransmissions of the first message on the first set of carriers. In someaspects, a different power level is used for the retransmission than forthe unsuccessful transmission. In some aspects, the different powerlevel is based at least in part on performance of an open loop powercontrol process for the second set of carriers. In some aspects, a samepower level is used for the retransmission and for the unsuccessfultransmission.

In some aspects, selectively performing the RACH procedure comprisestransmitting an uplink message, based at least in part on a TPC message,using the first set of carriers or the second set of carriers, whereinthe TPC message is interpreted based at least in part on whether theuplink message is transmitted using the first set of carriers or thesecond set of carriers.

In some aspects, selectively performing the RACH procedure comprisestransmitting an uplink message, based at least in part on a TPC message,using the first set of carriers or the second set of carriers, whereinthe TPC message is associated with a different number of bits based atleast in part on whether the uplink message is transmitted using thefirst set of carriers or the second set of carriers.

In some aspects, selectively performing the RACH procedure comprisestransmitting an uplink message, based at least in part on a TPC message,using the first set of carriers or the second set of carriers, whereinthe uplink message is associated with a particular waveform ornumerology based at least in part on whether the uplink message istransmitted using the first set of carriers or the second set ofcarriers.

In some aspects, selectively performing the RACH procedure comprisestransmitting an uplink message, based at least in part on a TPC message,using the first set of carriers or the second set of carriers, whereinthe uplink message is a third message of the RACH procedure.

In some aspects, selectively performing the RACH procedure comprisestransmitting an uplink message, based at least in part on a TPC message,using the first set of carriers or the second set of carriers, whereinthe uplink message is associated with a grant, wherein the grant isformatted differently based at least in part on whether the uplinkmessage is transmitted using the first set of carriers or the second setof carriers.

In some aspects, at least one of a resource allocation, a TPC messagebit width, or a channel quality information (CQI) request bit isformatted differently based at least in part on whether the uplinkmessage is transmitted using the first set of carriers or the second setof carriers.

In some aspects, a random access radio network temporary identifier(RA-RNTI) of the user equipment is determined based at least in part ona particular set of carriers, of the first set of carriers and thesecond set of carriers, with regard to which the RACH procedure isperformed.

In some aspects, a random access radio network temporary identifier(RA-RNTI) for a random access response (RAR) of the RACH procedureidentifies a particular set of carriers, of the first set of carriersand the second set of carriers, on which the RACH procedure isperformed.

Although FIG. 10 shows example blocks of process 1000, in some aspects,process 1000 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 10.Additionally, or alternatively, two or more of the blocks of process1000 may be performed in parallel.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the aspects to the preciseform disclosed. Modifications and variations are possible in light ofthe above disclosure or may be acquired from practice of the aspects.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software. Asused herein, a processor is implemented in hardware, firmware, or acombination of hardware and software.

Some aspects are described herein in connection with thresholds. As usedherein, satisfying a threshold may refer to a value being greater thanthe threshold, greater than or equal to the threshold, less than thethreshold, less than or equal to the threshold, equal to the threshold,not equal to the threshold, and/or the like.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the aspects. Thus, the operation and behavior of thesystems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based, at leastin part, on the description herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible aspects. In fact, many ofthese features may be combined in ways not specifically recited in theclaims and/or disclosed in the specification. Although each dependentclaim listed below may directly depend on only one claim, the disclosureof possible aspects includes each dependent claim in combination withevery other claim in the claim set. A phrase referring to “at least oneof” a list of items refers to any combination of those items, includingsingle members. As an example, “at least one of: a, b, or c” is intendedto cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combinationwith multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c,a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering ofa, b, and c).

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the terms “set” and “group” are intended to include oneor more items (e.g., related items, unrelated items, a combination ofrelated and unrelated items, etc.), and may be used interchangeably with“one or more.” Where only one item is intended, the term “one” orsimilar language is used. Also, as used herein, the terms “has,” “have,”“having,” and/or the like are intended to be open-ended terms. Further,the phrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method of wireless communication performed by auser equipment, comprising: receiving random access channel (RACH)configuration information, wherein the RACH configuration informationincludes: a threshold associated with a first set of carriers and asecond set of carriers, wherein the first set of carriers includes anuplink carrier that is a primary uplink carrier, and wherein the secondset of carriers includes an uplink carrier that is a supplementaryuplink carrier; and selectively performing a RACH procedure with regardto the first set of carriers or the second set of carriers based atleast in part on the RACH configuration information.
 2. The method ofclaim 1, wherein the first set of carriers is associated with a higherfrequency band than the second set of carriers.
 3. The method of claim1, wherein the RACH configuration information is received in systeminformation or radio resource control configuration information of theuser equipment.
 4. The method of claim 1, wherein the user equipment isconfigured to perform the RACH procedure with regard to a particular setof carriers, of the first set of carriers and the second set ofcarriers, associated with a lowest frequency band supported by the userequipment.
 5. The method of claim 4, wherein the RACH procedure isperformed with regard to the particular set of carriers usinginformation, of the RACH configuration information, that is pertinent tothe particular set of carriers.
 6. The method of claim 1, wherein theuser equipment is configured to select a particular set of carriers, ofthe first set of carriers and the second set of carriers, to use toperform the RACH procedure based at least in part on the threshold. 7.The method of claim 6, wherein the threshold is configured to balance aload, relating to the RACH procedure, between the first set of carriersand the second set of carriers.
 8. The method of claim 6, wherein thethreshold is based at least in part on a hash function performed usingan identifier associated with the user equipment.
 9. The method of claim1, wherein the user equipment is configured to perform the RACHprocedure with regard to a particular set of carriers, of the first setof carriers and the second set of carriers, based at least in part on aflag or value received by the user equipment and indicating to performthe RACH procedure with regard to the particular set of carriers. 10.The method of claim 1, wherein a random access radio network temporaryidentifier (RA-RNTI) of the user equipment is determined based at leastin part on a particular set of carriers, of the first set of carriersand the second set of carriers, with regard to which the RACH procedureis performed.
 11. The method of claim 1, wherein a random access radionetwork temporary identifier (RA-RNTI) for a random access response(RAR) of the RACH procedure identifies a particular set of carriers, ofthe first set of carriers and the second set of carriers, on which theRACH procedure is performed.
 12. The method of claim 1, wherein the RACHconfiguration information is received on a downlink carrier of the firstset of carriers.
 13. A user equipment (UE) for wireless communication,comprising: memory; and one or more processors operatively coupled tothe memory, the memory and the one or more processors configured to:receive random access channel (RACH) configuration information, whereinthe RACH configuration information includes: a threshold associated witha first set of carriers and a second set of carriers, wherein the firstset of carriers includes an uplink carrier that is a primary uplinkcarrier, and wherein the second set of carriers includes an uplinkcarrier that is a supplementary uplink carrier; and selectively performa RACH procedure with regard to the first set of carriers or the secondset of carriers based at least in part on the RACH configurationinformation.
 14. The UE of claim 13, wherein the first set of carriersis associated with a higher frequency band than the second set ofcarriers.
 15. The UE of claim 13, wherein the RACH configurationinformation is received in system information or radio resource controlconfiguration information of the UE.
 16. The UE of claim 13, wherein theUE is configured to perform the RACH procedure with regard to aparticular set of carriers, of the first set of carriers and the secondset of carriers, associated with a lowest frequency band supported bythe UE.
 17. The UE of claim 16, wherein the RACH procedure is performedwith regard to the particular set of carriers using information, of theRACH configuration information, that is pertinent to the particular setof carriers.
 18. The UE of claim 13, wherein the UE is configured toselect a particular set of carriers, of the first set of carriers andthe second set of carriers, to use to perform the RACH procedure basedat least in part on the threshold.
 19. The UE of claim 18, wherein thethreshold is configured to balance a load, relating to the RACHprocedure, between the first set of carriers and the second set ofcarriers.
 20. The UE of claim 18, wherein the threshold is based atleast in part on a hash function performed using an identifierassociated with the UE.
 21. The UE of claim 13, wherein the UE isconfigured to perform the RACH procedure with regard to a particular setof carriers, of the first set of carriers and the second set ofcarriers, based at least in part on a flag or value received by the UEand indicating to perform the RACH procedure with regard to theparticular set of carriers.
 22. The UE of claim 13, wherein a randomaccess radio network temporary identifier (RA-RNTI) of the UE isdetermined based at least in part on a particular set of carriers, ofthe first set of carriers and the second set of carriers, with regard towhich the RACH procedure is performed.
 23. The UE of claim 13, wherein arandom access radio network temporary identifier (RA-RNTI) for a randomaccess response (RAR) of the RACH procedure identifies a particular setof carriers, of the first set of carriers and the second set ofcarriers, on which the RACH procedure is performed.
 24. A non-transitorycomputer-readable medium storing one or more instructions for wirelesscommunication, the one or more instructions comprising: one or moreinstructions that, when executed by one or more processors of a userequipment (UE), cause the one or more processors to: receive randomaccess channel (RACH) configuration information, wherein the RACHconfiguration information includes: a threshold associated with a firstset of carriers and a second set of carriers, wherein the first set ofcarriers includes an uplink carrier that is a primary uplink carrier,and wherein the second set of carriers includes an uplink carrier thatis a supplementary uplink carrier; and selectively perform a RACHprocedure with regard to the first set of carriers or the second set ofcarriers based at least in part on the RACH configuration information.25. The non-transitory computer-readable medium of claim 24, wherein thefirst set of carriers is associated with a higher frequency band thanthe second set of carriers.
 26. The UE of claim 13, wherein the RACHconfiguration information is received on a downlink carrier of the firstset of carriers.
 27. The non-transitory computer-readable medium ofclaim 24, wherein the UE is configured to select a particular set ofcarriers, of the first set of carriers and the second set of carriers,to use to perform the RACH procedure based at least in part on thethreshold.
 28. The non-transitory computer-readable medium of claim 27,wherein the threshold is configured to balance a load, relating to theRACH procedure, between the first set of carriers and the second set ofcarriers.
 29. The non-transitory computer-readable medium of claim 27,wherein the threshold is based at least in part on a hash functionperformed using an identifier associated with the UE.
 30. Thenon-transitory computer-readable medium of claim 24, wherein a randomaccess radio network temporary identifier (RA-RNTI) of the UE isdetermined based at least in part on a particular set of carriers, ofthe first set of carriers and the second set of carriers, with regard towhich the RACH procedure is performed.
 31. The non-transitorycomputer-readable medium of claim 24, wherein a random access radionetwork temporary identifier (RA-RNTI) for a random access response(RAR) of the RACH procedure identifies a particular set of carriers, ofthe first set of carriers and the second set of carriers, on which theRACH procedure is performed.
 32. An apparatus for wirelesscommunication, comprising: means for receiving random access channel(RACH) configuration information, wherein the RACH configurationinformation includes: a threshold associated with a first set ofcarriers and a second set of carriers, wherein the first set of carriersincludes an uplink carrier that is a primary uplink carrier, and whereinthe second set of carriers includes an uplink carrier that is asupplementary uplink carrier; and means for selectively performing aRACH procedure with regard to the first set of carriers or the secondset of carriers based at least in part on the RACH configurationinformation.
 33. The non-transitory computer-readable medium of claim24, wherein the RACH configuration information is received on a downlinkcarrier of the first set of carriers.
 34. The apparatus of claim 32,wherein the first set of carriers is associated with a higher frequencyband than the second set of carriers.
 35. The apparatus of claim 32,wherein the apparatus is configured to select a particular set ofcarriers, of the first set of carriers and the second set of carriers,to use to perform the RACH procedure based at least in part on thethreshold.
 36. The apparatus of claim 35, wherein the threshold isconfigured to balance a load, relating to the RACH procedure, betweenthe first set of carriers and the second set of carriers.
 37. Theapparatus of claim 35, wherein the threshold is based at least in parton a hash function performed using an identifier associated with theapparatus.
 38. The apparatus of claim 32, wherein a random access radionetwork temporary identifier (RA-RNTI) of the apparatus is determinedbased at least in part on a particular set of carriers, of the first setof carriers and the second set of carriers, with regard to which theRACH procedure is performed.
 39. The apparatus of claim 32, wherein arandom access radio network temporary identifier (RA-RNTI) for a randomaccess response (RAR) of the RACH procedure identifies a particular setof carriers, of the first set of carriers and the second set ofcarriers, on which the RACH procedure is performed.
 40. The apparatus ofclaim 32, wherein the RACH configuration information is received on adownlink carrier of the first set of carriers.